Repository navigation
Embed the testifylint analyzer - #37
Merged
Merged
Conversation
testify has no type-level check for a misuse such as assert.True on a comparison, and testifylint reports it. Its analyzer needs the inspect analyzer, which the driver already supplies for the analyzer graph. analysistest loads testdata in GOPATH mode, where the real testify module is not reachable. The testdata holds a stub of the assert package under the import path that testifylint matches. The stub carries the calls the testdata makes, so the test needs no network and no module file. Change-Id: I67d235f00fe3e741dc1fc89ac213b97deb3003d3
nnutter
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.